Forge Authentication

Agentty uses plain Git for branch publishing and then uses the forge CLI for pull-request or merge-request actions.

That split matters:

  • p always runs git push first.
  • GitHub and GitLab CLI login only covers the forge CLI.
  • HTTPS remotes still need Git transport credentials when Git performs the push.

For the session-view publish flow, see Workflow.

GitHub🔗

Use this setup when the repository remote is on GitHub.

  1. Run gh auth login.
  2. Choose the target host such as github.com.
  3. Pick the Git protocol Agentty should use for branch publishing: https or ssh.
  4. If you picked https, run gh auth setup-git after login so Git can use gh as a credential helper for branch pushes.
  5. Verify the setup with gh auth status.

With that setup:

  • p pushes through Git and then uses gh to create or refresh the pull request.

GitLab🔗

Use this setup when the repository remote is on GitLab.

  1. Run glab auth login.
  2. Choose the target host such as gitlab.com or your self-hosted hostname.
  3. Pick the Git protocol Agentty should use for branch publishing: https or ssh.
  4. Verify the CLI login with glab auth status --hostname <hostname>.
  5. If you picked https, also configure Git itself for HTTPS pushes: either a credential helper or a personal access token that Git can use when git push prompts for credentials.

With that setup:

  • p uses plain git push first, then uses glab to create or refresh the merge request.

If glab auth status says you are authenticated but Agentty still reports a push-authentication failure, the missing piece is Git HTTPS credentials rather than glab authentication.